Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1166

reference: 177-tree-1
name: 1166
tree-preservation-order: undefined
177-tpo-1
uprn
address-text
point: POINT (-0.943563 50.858976)
geometry: MULTIPOLYGON (((-0.943535 50.858973,-0.943536 50.858978,-0.943540 50.858983,-0.943546 50.858987,-0.943554 50.858990,-0.943563 50.858991,-0.943579 50.858988,-0.943586 50.858984,-0.943590 50.858979,-0.943591 50.858973,-0.943590 50.858968,-0.943586 50.858963,-0.943580 50.858959,-0.943572 50.858956,-0.943563 50.858955,-0.943547 50.858958,-0.943540 50.858962,-0.943536 50.858967,-0.943535 50.858973)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL